Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fce5b7f45aeaba8189cd9431f0fdc03322a5979a15312fe22605e84bd6173d9

Tx prefix hash: c3827f5b31818475dbd7a2b9c016a957bb56e5182468a716df52bdad43578f16
Tx public key: c4bdbb8f23a7fa1efa54474f36b056874e31d5aa5267cdfd53504d4be5630930
Timestamp: 1746375437 Timestamp [UCT]: 2025-05-04 16:17:17 Age [y:d:h:m:s]: 00:200:21:51:37
Block: 1275696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141299 RingCT/type: yes/0
Extra: 01c4bdbb8f23a7fa1efa54474f36b056874e31d5aa5267cdfd53504d4be56309300211000000091f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc4906f9bc77b5fe7458df683d3ba68d1068d55d206414ae0971198e1c6ff97f 0.600000000000 1763011 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": 1275706, "vin": [ { "gen": { "height": 1275696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc4906f9bc77b5fe7458df683d3ba68d1068d55d206414ae0971198e1c6ff97f" } } ], "extra": [ 1, 196, 189, 187, 143, 35, 167, 250, 30, 250, 84, 71, 79, 54, 176, 86, 135, 78, 49, 213, 170, 82, 103, 205, 253, 83, 80, 77, 75, 229, 99, 9, 48, 2, 17, 0, 0, 0, 9, 31, 144, 81, 122, 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