Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80cc54a2d811dc930666507e2bd42ab950a7ef729010c9fb73186f5b5497b3e1

Tx prefix hash: 0e5995c5b478cc2e3fbf74c4f9801ac9111055aa10c70a22af70bc47b3cf03d7
Tx public key: 7e0905f89ab008a1d00565bff3ff9d7583c7e7e7d20130edbac63a25e2171c0e
Timestamp: 1754432559 Timestamp [UCT]: 2025-08-05 22:22:39 Age [y:d:h:m:s]: 00:155:04:55:56
Block: 1341064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109991 RingCT/type: yes/0
Extra: 017e0905f89ab008a1d00565bff3ff9d7583c7e7e7d20130edbac63a25e2171c0e021100000021b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab32fcf3cd56171b0751d1b5769527fe50bf05f860d5b185ff87ce18dc1f0274 0.600000000000 1828885 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": 1341074, "vin": [ { "gen": { "height": 1341064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab32fcf3cd56171b0751d1b5769527fe50bf05f860d5b185ff87ce18dc1f0274" } } ], "extra": [ 1, 126, 9, 5, 248, 154, 176, 8, 161, 208, 5, 101, 191, 243, 255, 157, 117, 131, 199, 231, 231, 210, 1, 48, 237, 186, 198, 58, 37, 226, 23, 28, 14, 2, 17, 0, 0, 0, 33, 178, 247, 132, 196, 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