Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ce348ef620fbb5bd75d6cba9be96e7832ebcb1fc5104cd763881b32021d9aff

Tx prefix hash: 2cfe15115f9f14cfbd91fc2e909d1d8398975a40564c24fbeaf23dd6107e4251
Tx public key: 311c9c13f27f2de4f4b333eb4303de5703aebdc4146c84ac28354af821798b5c
Timestamp: 1722053727 Timestamp [UCT]: 2024-07-27 04:15:27 Age [y:d:h:m:s]: 00:289:09:19:14
Block: 1074575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206764 RingCT/type: yes/0
Extra: 01311c9c13f27f2de4f4b333eb4303de5703aebdc4146c84ac28354af821798b5c021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 510e7c512ce3508ce5ecd4e4a2af4b59ad71581b9f5a48213f3d0d22c947e866 0.600000000000 1547090 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": 1074585, "vin": [ { "gen": { "height": 1074575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "510e7c512ce3508ce5ecd4e4a2af4b59ad71581b9f5a48213f3d0d22c947e866" } } ], "extra": [ 1, 49, 28, 156, 19, 242, 127, 45, 228, 244, 179, 51, 235, 67, 3, 222, 87, 3, 174, 189, 196, 20, 108, 132, 172, 40, 53, 74, 248, 33, 121, 139, 92, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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