Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68fbf726a699095b544fab95652bbc0c26e84e2e92fcdbfefb418dc0e511fed1

Tx prefix hash: f2728756f00fbfcd0c6b00e8d57222fc828857542198cbd52e05f8b7ba3cd4b5
Tx public key: 0f2c617310fdd880946400e30007e5460e60331a86d6c9aa874e06f0853fbe92
Timestamp: 1677630538 Timestamp [UCT]: 2023-03-01 00:28:58 Age [y:d:h:m:s]: 01:362:22:35:39
Block: 707172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520076 RingCT/type: yes/0
Extra: 010f2c617310fdd880946400e30007e5460e60331a86d6c9aa874e06f0853fbe92021100000001835e4d22000000000000000000

1 output(s) for total of 2.785130221000 dcy

stealth address amount amount idx
00: a74ce8def41f4f9f442757014eaa4f13c30f794a04c54dc686b8ed5589ebf124 2.785130221000 1150969 of 0

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": 707182, "vin": [ { "gen": { "height": 707172 } } ], "vout": [ { "amount": 2785130221, "target": { "key": "a74ce8def41f4f9f442757014eaa4f13c30f794a04c54dc686b8ed5589ebf124" } } ], "extra": [ 1, 15, 44, 97, 115, 16, 253, 216, 128, 148, 100, 0, 227, 0, 7, 229, 70, 14, 96, 51, 26, 134, 214, 201, 170, 135, 78, 6, 240, 133, 63, 190, 146, 2, 17, 0, 0, 0, 1, 131, 94, 77, 34, 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