Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 744e7aff9757ad3d65be7bc92499698996309ca8621a3ba3a27ea25dadf85557

Tx prefix hash: 922c1c179a7af445b4d335e53156841b6e7a5a74cd2b86c2c4d6fad7676e1425
Tx public key: cbcfea1bb6ce912a3d84ae17a844dd70d5398486e9cc927e7b2d74bcd23625da
Timestamp: 1736078969 Timestamp [UCT]: 2025-01-05 12:09:29 Age [y:d:h:m:s]: 00:164:02:08:26
Block: 1190731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116966 RingCT/type: yes/0
Extra: 01cbcfea1bb6ce912a3d84ae17a844dd70d5398486e9cc927e7b2d74bcd23625da02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a594a87f8585d79e62bc290570792235f1679afa75c8c58fbcf51401d4fc9c0e 0.600000000000 1677250 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": 1190741, "vin": [ { "gen": { "height": 1190731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a594a87f8585d79e62bc290570792235f1679afa75c8c58fbcf51401d4fc9c0e" } } ], "extra": [ 1, 203, 207, 234, 27, 182, 206, 145, 42, 61, 132, 174, 23, 168, 68, 221, 112, 213, 57, 132, 134, 233, 204, 146, 126, 123, 45, 116, 188, 210, 54, 37, 218, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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