Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 300eb28824fc42ff532804e79401b2494bf81292bff3b602fe5d1d2f5ecc71d7

Tx prefix hash: 6583a464c44b9b8b6cb6c150e034b4bc03563845a0750eed83f2b56279f9c595
Tx public key: b4ce70e5c55cf95846de5be2739c8972624ecf07c8e876afa77f30f91f986997
Timestamp: 1745504573 Timestamp [UCT]: 2025-04-24 14:22:53 Age [y:d:h:m:s]: 00:211:02:56:53
Block: 1268496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148594 RingCT/type: yes/0
Extra: 01b4ce70e5c55cf95846de5be2739c8972624ecf07c8e876afa77f30f91f9869970211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73142da974129b6dc2da2b7fe3859d2e8a68f3733c3c5c72b70dd094c1b3b282 0.600000000000 1755725 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1268506, "vin": [ { "gen": { "height": 1268496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73142da974129b6dc2da2b7fe3859d2e8a68f3733c3c5c72b70dd094c1b3b282" } } ], "extra": [ 1, 180, 206, 112, 229, 197, 92, 249, 88, 70, 222, 91, 226, 115, 156, 137, 114, 98, 78, 207, 7, 200, 232, 118, 175, 167, 127, 48, 249, 31, 152, 105, 151, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8