Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4de36c5ab9a19ef5a135f6a3687c6ee9396c3882d8c698a688dce8035245407

Tx prefix hash: d34169249c5392a535d082a6f0fa11686ee3cfa954eb71e4a20925ae5fc493f3
Tx public key: 79724bd51dccb981f21319f61eedc2b8008637988eeecb70f44d5c2e4faf6a63
Timestamp: 1728474976 Timestamp [UCT]: 2024-10-09 11:56:16 Age [y:d:h:m:s]: 00:184:03:17:33
Block: 1127814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131405 RingCT/type: yes/0
Extra: 0179724bd51dccb981f21319f61eedc2b8008637988eeecb70f44d5c2e4faf6a6302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79fee1567cafefc76eb60c6745a34ce6f9e0f7f8706742d0b77d0ac44e01379a 0.600000000000 1610627 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": 1127824, "vin": [ { "gen": { "height": 1127814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79fee1567cafefc76eb60c6745a34ce6f9e0f7f8706742d0b77d0ac44e01379a" } } ], "extra": [ 1, 121, 114, 75, 213, 29, 204, 185, 129, 242, 19, 25, 246, 30, 237, 194, 184, 0, 134, 55, 152, 142, 238, 203, 112, 244, 77, 92, 46, 79, 175, 106, 99, 2, 17, 0, 0, 0, 1, 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