Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c0c576c128ad515eb02666452d129ffbc9c1ed6e006b5298f40fe3bb6177f61

Tx prefix hash: e7c68e2cc9332dd97eb9dc1d8a5c1e1d260e11321351c84f7cd5ff3bff15c294
Tx public key: 130fe119e8971e4116d74e4ef5fcccce9d43b3bf2ef124fe30617bd5b1f26ea6
Timestamp: 1709914381 Timestamp [UCT]: 2024-03-08 16:13:01 Age [y:d:h:m:s]: 01:072:19:14:58
Block: 973946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313057 RingCT/type: yes/0
Extra: 01130fe119e8971e4116d74e4ef5fcccce9d43b3bf2ef124fe30617bd5b1f26ea602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdf081b83072c56cd2d55589291bb7473ad6b3a5baaa54c4e040746d398b83c4 0.600000000000 1433889 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": 973956, "vin": [ { "gen": { "height": 973946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdf081b83072c56cd2d55589291bb7473ad6b3a5baaa54c4e040746d398b83c4" } } ], "extra": [ 1, 19, 15, 225, 25, 232, 151, 30, 65, 22, 215, 78, 78, 245, 252, 204, 206, 157, 67, 179, 191, 46, 241, 36, 254, 48, 97, 123, 213, 177, 242, 110, 166, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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