Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca1d1523ae53bd2d50a8704425712d09ad13828ddb04df15fa34c51468a83813

Tx prefix hash: 9b7cb3c82cfa77e56ecdd4814a0f1be7cee1f3917e4b82128308086147e4a450
Tx public key: 86f8927ced070ee10d40738e1cb5c5da624ba3c2646b4e823b6e39f478300b5e
Timestamp: 1673012932 Timestamp [UCT]: 2023-01-06 13:48:52 Age [y:d:h:m:s]: 02:023:10:06:20
Block: 668865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538404 RingCT/type: yes/0
Extra: 0186f8927ced070ee10d40738e1cb5c5da624ba3c2646b4e823b6e39f478300b5e02110000000152542ceb000000000000000000

1 output(s) for total of 3.730547334000 dcy

stealth address amount amount idx
00: 76a3b186f7ebe9e03952aa4138797c1ea1ba14381808ffcac0e5d9bf46ec2a54 3.730547334000 1110136 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": 668875, "vin": [ { "gen": { "height": 668865 } } ], "vout": [ { "amount": 3730547334, "target": { "key": "76a3b186f7ebe9e03952aa4138797c1ea1ba14381808ffcac0e5d9bf46ec2a54" } } ], "extra": [ 1, 134, 248, 146, 124, 237, 7, 14, 225, 13, 64, 115, 142, 28, 181, 197, 218, 98, 75, 163, 194, 100, 107, 78, 130, 59, 110, 57, 244, 120, 48, 11, 94, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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