Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a5eff78af839cb5fbc01c3a913f89a723de3d2ef3f3ac06e89b462ec0b9461a

Tx prefix hash: 697b9d76553d500490034f8eb95e311eb11456066d39e22cf089531bbe37b6f8
Tx public key: 376b99cbcd86545ab6f53fe0574eb020e2915df74e6038b0f1b7a00a060a46f2
Timestamp: 1727492637 Timestamp [UCT]: 2024-09-28 03:03:57 Age [y:d:h:m:s]: 00:025:01:32:02
Block: 1119677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17919 RingCT/type: yes/0
Extra: 01376b99cbcd86545ab6f53fe0574eb020e2915df74e6038b0f1b7a00a060a46f202110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79abd747f05bffc0a77a1e278f66d0e6921a83f4bef05ad2fcea82ae0a7347c7 0.600000000000 1601320 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": 1119687, "vin": [ { "gen": { "height": 1119677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79abd747f05bffc0a77a1e278f66d0e6921a83f4bef05ad2fcea82ae0a7347c7" } } ], "extra": [ 1, 55, 107, 153, 203, 205, 134, 84, 90, 182, 245, 63, 224, 87, 78, 176, 32, 226, 145, 93, 247, 78, 96, 56, 176, 241, 183, 160, 10, 6, 10, 70, 242, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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