Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fd2b58cf4623d03cde8c64772d245bf3476e3951625551c63a3660f5e1dd910

Tx prefix hash: 67c05d79d955c5220c069f2ac1a600c85cbb7617a65f611eaa53774e5bae2489
Tx public key: 828531c67b67efb9faae6fd85ad4e7a05ba212c1680b1d4cf68ef4b706e464bf
Timestamp: 1735664165 Timestamp [UCT]: 2024-12-31 16:56:05 Age [y:d:h:m:s]: 00:166:13:11:12
Block: 1187276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118776 RingCT/type: yes/0
Extra: 01828531c67b67efb9faae6fd85ad4e7a05ba212c1680b1d4cf68ef4b706e464bf021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03fa03d1874e8425db39c6de7dc473d118f37368c4335b01d6fa6f28d9379f48 0.600000000000 1673765 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": 1187286, "vin": [ { "gen": { "height": 1187276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03fa03d1874e8425db39c6de7dc473d118f37368c4335b01d6fa6f28d9379f48" } } ], "extra": [ 1, 130, 133, 49, 198, 123, 103, 239, 185, 250, 174, 111, 216, 90, 212, 231, 160, 91, 162, 18, 193, 104, 11, 29, 76, 246, 142, 244, 183, 6, 228, 100, 191, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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