Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56eca52f1e26ddbcd52ed33f23b20e184bf236f8faa4df639e10a9776ba4a39b

Tx prefix hash: 51dcc6d07e27b06e0752f51be2460e1d93ac1d19b681a336b56fb84798921a27
Tx public key: 5ae2814bbc7f491a985bbc73696b135798dae575bdb07fbdb5d6fb718f8aa924
Timestamp: 1765904585 Timestamp [UCT]: 2025-12-16 17:03:05 Age [y:d:h:m:s]: 00:020:06:33:46
Block: 1434986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14545 RingCT/type: yes/0
Extra: 015ae2814bbc7f491a985bbc73696b135798dae575bdb07fbdb5d6fb718f8aa9240211000000087b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0229acb193f0d8a265b12501c484a864baaa6f726b0fc7490d9d3f1359ba9796 0.600000000000 1923783 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": 1434996, "vin": [ { "gen": { "height": 1434986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0229acb193f0d8a265b12501c484a864baaa6f726b0fc7490d9d3f1359ba9796" } } ], "extra": [ 1, 90, 226, 129, 75, 188, 127, 73, 26, 152, 91, 188, 115, 105, 107, 19, 87, 152, 218, 229, 117, 189, 176, 127, 189, 181, 214, 251, 113, 143, 138, 169, 36, 2, 17, 0, 0, 0, 8, 123, 30, 81, 172, 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