Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee364bc9360b6a9cb01c2c26b31f7bda902d12612e5ccfb1e1afb2559267e797

Tx prefix hash: b2d147942254412ea86e3125f54175f053218551ce9d2d6c622292714f0d9c8f
Tx public key: 0ec62061195859fbf4874b30661f26c8ff11df89c4f2378889c4f3fc7c0b9438
Timestamp: 1736111265 Timestamp [UCT]: 2025-01-05 21:07:45 Age [y:d:h:m:s]: 00:101:08:21:00
Block: 1191004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72200 RingCT/type: yes/0
Extra: 010ec62061195859fbf4874b30661f26c8ff11df89c4f2378889c4f3fc7c0b9438021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ceb320a298f16c25b091485a572a9e2516167da1d5aba8dd1a1d9b821910af7 0.600000000000 1677527 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": 1191014, "vin": [ { "gen": { "height": 1191004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ceb320a298f16c25b091485a572a9e2516167da1d5aba8dd1a1d9b821910af7" } } ], "extra": [ 1, 14, 198, 32, 97, 25, 88, 89, 251, 244, 135, 75, 48, 102, 31, 38, 200, 255, 17, 223, 137, 196, 242, 55, 136, 137, 196, 243, 252, 124, 11, 148, 56, 2, 17, 0, 0, 0, 7, 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