Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf863fc2f44eadc5577d3b8f1005789a1adcff1ba5169deb4ddbdae4fd5de4ab

Tx prefix hash: 5215c0e4bd65870eaccbdc3203c439787b6b07ce7a45c237fece8e2315ac1c72
Tx public key: 41227eac323b43e5cbc83ec925e67248e15ae10c19944d18c6e99ba1419b15b8
Timestamp: 1736975073 Timestamp [UCT]: 2025-01-15 21:04:33 Age [y:d:h:m:s]: 00:154:19:29:48
Block: 1198133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110352 RingCT/type: yes/0
Extra: 0141227eac323b43e5cbc83ec925e67248e15ae10c19944d18c6e99ba1419b15b8021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57b6208bfe74d95c7f000013f2b648857a1a6760797390c6965d80dc9adafe54 0.600000000000 1684752 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": 1198143, "vin": [ { "gen": { "height": 1198133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57b6208bfe74d95c7f000013f2b648857a1a6760797390c6965d80dc9adafe54" } } ], "extra": [ 1, 65, 34, 126, 172, 50, 59, 67, 229, 203, 200, 62, 201, 37, 230, 114, 72, 225, 90, 225, 12, 25, 148, 77, 24, 198, 233, 155, 161, 65, 155, 21, 184, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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